How long does it take for Konnect inputs to become useable after the Initialisation command?

The reason I ask, is I've got my Stepper drive fault signals connected to a Konnect, and as part of my init.c, I test that the signals are all present (if they're not, it kickstarts a drive reset cycle), and it's currently triggering the drive reset cycle despite all drives not being in fault.

I'm assuming it's because it's the first thing that gets tested after the Konnect is initialised, and the virtual bits have not been updated, before I'm testing the inputs. I'm guessing a simple delay will cure the problem.

Also, while on the subject of Konnect's, what happens if a Konnect was to stop updating?

I've got a couple critical inputs and outputs connected to it, and have just thought I've got no idea what would happen if it was to stop updating. I know it's current output state remains, but what does the KFlop do?

Thanks,

Moray

Hi Moray,

It should take 2 Time Slices for Konnect to be initialized and the IO updated.

Konnect should never stop updating unless there is a communication error detected which displays a Console message and then goes idle.

I've attached a program to test if Konnect Servicing has gone idle.

Regards
TK

On 11/12/2017 1:35 PM, moray.cuthill@... [DynoMotion] wrote:

How long does it take for Konnect inputs to become useable after the Initialisation command?

The reason I ask, is I've got my Stepper drive fault signals connected to a Konnect, and as part of my init.c, I test that the signals are all present (if they're not, it kickstarts a drive reset cycle), and it's currently triggering the drive reset cycle despite all drives not being in fault.

I'm assuming it's because it's the first thing that gets tested after the Konnect is initialised, and the virtual bits have not been updated, before I'm testing the inputs. I'm guessing a simple delay will cure the problem.

Also, while on the subject of Konnect's, what happens if a Konnect was to stop updating?

I've got a couple critical inputs and outputs connected to it, and have just thought I've got no idea what would happen if it was to stop updating. I know it's current output state remains, but what does the KFlop do?

Thanks,

Moray

Thanks for that.

I've went for the simple option of adding a 0.1 second delay after the Konnect Init, which has cured the problem.

I'll get your sample code added to my EStop monitoring, so things get stopped should something happen to the Konnect.

Moray

On Mon, Nov 13, 2017 at 7:26 PM, Tom Kerekes tk@... [DynoMotion] <DynoMotion@yahoogroups.com> wrote:

Hi Moray,

It should take 2 Time Slices for Konnect to be initialized and the IO updated.

Konnect should never stop updating unless there is a communication error detected which displays a Console message and then goes idle.

I've attached a program to test if Konnect Servicing has gone idle.

Regards
TK

On 11/12/2017 1:35 PM, moray.cuthill@... [DynoMotion] wrote:

How long does it take for Konnect inputs to become useable after the Initialisation command?

The reason I ask, is I've got my Stepper drive fault signals connected to a Konnect, and as part of my init.c, I test that the signals are all present (if they're not, it kickstarts a drive reset cycle), and it's currently triggering the drive reset cycle despite all drives not being in fault.

I'm assuming it's because it's the first thing that gets tested after the Konnect is initialised, and the virtual bits have not been updated, before I'm testing the inputs. I'm guessing a simple delay will cure the problem.

Also, while on the subject of Konnect's, what happens if a Konnect was to stop updating?

I've got a couple critical inputs and outputs connected to it, and have just thought I've got no idea what would happen if it was to stop updating. I know it's current output state remains, but what does the KFlop do?

Thanks,

Moray

Group: DynoMotion	Message: 15151	From: moray_cuthill	Date: 11/12/2017
Subject: Konnect Init time?

Group: DynoMotion	Message: 15155	From: Tom Kerekes	Date: 11/13/2017
Subject: Re: Konnect Init time?

Group: DynoMotion	Message: 15158	From: Moray Cuthill	Date: 11/13/2017
Subject: Re: Konnect Init time?